Rescue time tracker

ABSTRACT

This document relates to systems and techniques for providing response to emergency situations, such as traffic accidents, cardiac arrest, or other medical emergencies.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation under 35 U.S.C. §120 of U.S. patentapplication Ser. No. 15/225,019, filed Aug. 1, 2016 which is acontinuation of U.S. patent application Ser. No. 14/830,940, filed Aug.20, 2015 and issued as U.S. Pat. No. 9,430,926, which is a continuationof U.S. patent application Ser. No. 14/584,131, filed Dec. 29, 2014 andabandoned, which is a continuation of U.S. patent application Ser. No.13/555,422, filed Jul. 23, 2012 and issued as U.S. Pat. No. 8,922,364,which claims benefit under 35 U.S.C. §119(e) to U.S. ProvisionalApplication Ser. No. 61/527,778 filed Aug. 26, 2011. All subject matterset forth in each of the above referenced applications is herebyincorporated by reference in their entirety into the present applicationas if fully set forth herein.

TECHNICAL FIELD

This document relates to systems and techniques for providing responseto emergency situations, such as traffic accidents, cardiac arrest, orother medical emergencies.

BACKGROUND

Sudden health problems such as sudden cardiac arrest and injuries causedby accidents kill thousands of people and cause permanent injury everyyear. Fast and competent care can be essential to positive outcomes insuch situations. For example, it is said that the chance of surviving asudden cardiac arrest falls by ten percent for every minute in delayingeffective treatment.

Emergency events like sudden cardiac arrests and accidents are generallyresponded to by organized emergency response units, such as ambulance orfire crews, and by laypeople who are immediately around the events sothat they personally witness or offer assistance for the events. Often,the laypeople in a victim's immediate vicinity are not trained to treatthe victim, or are too overwhelmed to provide effective treatment. Onthe other hand, the organized emergency response units may be far awayfrom the victim, so that they cannot arrive at the scene for a longtime.

SUMMARY

This document describes systems and techniques that may be used tocoordinate treatment of a victim among responders, including layresponders and/or professional responders. The systems and techniquesdescribed herein include a rescue time tracker that provides informationabout the amount of time elapsed since the first contact of a rescuerwith the victim. For example, a rescue time tracker can be affixed to avictim upon first contact of the rescuer with the victim and the rescuetime tracker can provide a current elapsed time (e.g., provide anincreasing time count beginning at contact) or a remaining length ofeffective treatment time (e.g., counting down from a pre-set total timewith the countdown beginning upon initial contact).

In some additional examples, the rescue time tracker may be programmedto receive and store information during a rescue event. The rescue timetracker can additionally format the various types of information thatwere gathered during the treatment into a report. For example,additional information about events during the treatment of the victimprior to the victim's arrival in the hospital (e.g., initiation of CPR,defibrillation, drug administration, ventilation, etc.) can be recordedwith the time from the rescue time tracker. Subsequently, the time countmaintained by the rescue time tracker can be coordinated with a standardtime (e.g., a time kept at the medical treatment facility) to provide atimeline of events during the rescue attempt.

In some additional examples, for a multiple-victim emergency or apotential mass casualty situation, separate rescue time trackers can beaffixed to each victim. Providing separate rescue time tracker on eachvictim at the scene of a multi-victim emergency can facilitate inprioritizing treatment of the victims by the responders. For example,responders may be assigned to provide assistance to those withparticular elapsed time ranges before providing assistance to othervictims. In another example, the rescue time tracker can additionallyallow input of an injury severity indicator and the responders may beassigned to provide assistance to those with particular injury severitylevels (or combinations of severity levels and elapsed times) beforeproviding assistance to other victims.

In some aspects, a rescue time tracking device for communicatinginformation to a rescuer includes an adhesive layer on a first side ofthe rescue time tracking device for affixing the rescue time trackingdevice to a victim, timing circuitry configured to maintain timeinformation relative to a time of initialization of the device, and adisplay portion on the second side of the rescue time tracking deviceconfigured to display the time information.

Embodiments can include one or more of the following.

The circuitry can be configured to maintain the time informationcomprises circuitry configured to initialize the device to a preset timeupon initialization of the device and decrement a time count from thepreset time subsequent to initialization of the device.

The circuitry can be configured to maintain the time informationcomprises circuitry configured to increment a time count from subsequentto initialization of the device.

The device can also include circuitry to determine when a predeterminedamount of time has elapsed subsequent to initialization of the deviceand apply a visual indicia to the time information on the displayportion upon the determination that the predetermined amount of time haselapsed.

The display portion can be further configured to display timeinformation for one or more events related to the victim.

The device can also include a plurality of input devices, each inputdevice being associated with an event, circuitry configured to recordtime information from the timing circuitry upon selection of aparticular one of the plurality of input devices.

The display portion can be configured to display the recorded currenttime information for the event.

The device can also include a wireless transmitter configured totransfer the time information to a computing device.

The device can also include a backing affixed to the backside of therescue time tracking device prior to initialization, wherein removal ofthe rescue time tracking device from the backing initializes the timingcircuitry.

In some additional aspects, a computer-implemented method forcommunicating information to one or more medical responders can includereceiving, from a plurality of rescue time tracking devices, at acentral computing device location information that identifies a currentlocation of a victim associated with a particular rescue time trackingdevice and time information from the rescue timing device and generatinga display that identifies the location of the victims associated withthe plurality of rescue timing devices and the timing information forthe plurality of rescue timing devices.

Embodiments can include one or more of the following.

The method can also include receiving location information for the oneor more medical responders.

Generating the display can include identifying the location of the oneor more medical responders based on the received location informationfor the one or more medical responders.

The method can also include color coding the location of the victims onthe display based on the timing information.

The time information can include a time count decremented from a presettotal time.

The time information can include an incrementing the time count with aninitial time for the time count being based on a time of initializationof the time counter device.

The details of one or more embodiments are set forth in the accompanyingdrawings and the description below. Other features and advantages willbe apparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a conceptual diagram showing emergency response.

FIGS. 2A-2C are diagrams of an exemplary rescue time tracker.

FIG. 3 is a diagram of an exemplary rescue time tracker.

FIG. 4 is a diagram of a multiple-victim emergency.

FIG. 5 is an exemplary display of a multiple-victim emergency.

FIG. 6A is a diagram of an exemplary rescue time tracker.

FIG. 6B shows an example of a timeline generated based on informationfrom a rescue time tracker.

FIG. 7 is a flow chart of a process for generating a rescue timeline.

FIG. 8 is a diagram of a computer system.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

Systems and techniques described herein include a rescue time trackerthat provides information about the length of time that has elapsedsince the first contact of a rescuer with the victim. A rescue timetracker can be affixed to a victim upon first contact of the rescuerwith the victim and the rescue time tracker can provide a currentelapsed time or a remaining amount of effective treatment time. Thetime-based information can provide guidance to a rescuer about how toeffectively treat the victim. In some additional examples, the timer canprovide information about the length of time that has elapsed since atime of dispatch of emergency response personnel, defibrillatorpower-on, time of arrival at the emergency department or other treatmentfacility, or time of symptom onset. The start time for the timer couldbe automatically transmitted from a tablet or AED or input directly intothe rescue time tracker via one or more inputs.

FIG. 1 is a diagram of a scene of an emergency. A rescuer 12 providesemergency treatment and assistance to a victim 14, such as a victimsuffering from sudden cardiac arrest or a victim at the scene of anaccident. Upon contact with the victim 14, the rescuer affixes a rescuetime tracker 10 to the victim. For example, the rescue time tracker 10can be applied using an adhesive substance to the victim's skin such ason the victim's hand, forehead, or chest. Alternatively, the rescue timetracker can be secured around the victim's wrist or ankle (e.g., asshown in FIG. 3). The rescue time tracker 10 provides a visual and/oraudible indication of the elapsed time subsequent to the victimexperiencing trauma or subsequent to the initial contact with the victimby a rescuer.

In some examples, rescue time tracker 10 can be a specialized type ofclock that acts as a timer and counts down from a specified timeinterval (e.g., a time interval established based on the condition ofthe victim) or that acts as a stopwatch counts upwards from zero formeasuring elapsed time. The rescue time tracker 10 can be mechanical,electromechanical, electronic (quartz), or even software-based.

The rescue time tracker 10 provides a visual indication to the rescueror to other medical personnel who come into contact with the victim 14regarding the length of time that has elapsed since contact with thevictim 14 was first established. The information can be presented as atotal elapsed time or as a time remaining for effective treatment. Therescuer or medical personnel can use the information from the rescuetime tracker 10 to guide decisions about care administered to thevictim. For example, if a large amount of time has elapsed since theinitiation of treatment and the victim 14 is still unresponsive to thetreatment more aggressive treatment options might be used than iftreatment had only recently been initiated.

In some examples, the rescue time tracker 10 can include additionalvisual indicia to provide information about the status of the victim 14.For example, time-based thresholds can be used to provide high-levelvisual information to the rescuer 12 about the length of time that haselapsed (in addition to the displayed time). For example, as the elapsedtime increases the color of the display can change.

In one particular example, during a first time period, the display canbe green, and then change to yellow during a second time period, andfinally to red during a third time period. The time periods can be basedon time thresholds associated with treatment of the condition. Forexample, for cardiac arrest, the counter could count down from 90minutes and display could be green from 90 minutes to 70 minutes, yellowfrom 69 minutes to 30 minutes, and red from 30 minutes to zero minutes.As such, even if the rescuer does not have knowledge about the length ofeffective treatment time for a particular condition, the rescuer 12 canstill receive feedback from the rescue time tracker 10 about the statusof the rescue and remaining time during which efforts to rescue thevictim 10 are likely to be effective.

FIGS. 2A-2C show an example of a rescue timer 10. More particularly,FIG. 2A shows the rescue timer 10 prior to initialization, FIG. 2B showsthe rescue timer 10 at the time of initialization, and FIG. 2C shows therescue timer 10 at a subsequent time during use of the rescue timer 10.

The rescue timer 10 includes a display portion 20 that displays a timecounter 22. The time counters 22 shown in FIG. 2A-2C displays minutesand seconds. Alternatively, the time can be displayed in other formatssuch as minutes only or hours and minutes.

As shown in FIG. 2A, prior to initialization, the time counter 22 caninitially be blank or show a non-time based entry such as xx:xx (asshown in FIG. 2A) to indicate that the device has not been previouslyused. Alternatively, the time counter 22 can display the initial timefor the counter prior to enabling the counter. For example, if thecounter is configured to count down a particular length of time the timecounter 22 can display to length of time (e.g., 90 minutes, 60 minutes)or if the counter is configured to count up the time counter 22 caninitially display 00:00 prior to initialization.

Prior to initialization, the rescue time tracker 10 can be affixed to abacking 24. Removal of the backing can initialize/enable the rescue timetracker 10. For example, the rescue time tracker can include a circuitthat is completed upon removal of the backing 24 or the backing 24 caninclude a portion prohibiting contact of a battery with a countercircuit prior to removal of backing 24 such that removal of the backing24 powers and initializes the rescue time tracker 10. In other examples,the rescue timer 10 can be enabled using other methods such asdepressing a button, removing a tab to allow contact with a battery,etc.

In some examples, the rescue time tracker 10 can be in the form of asticker with the display of the time counter on a front side of thesticker and an adhesive substance on a back side of the sticker. Removalof the backing 24 can expose an adhesive substance on a backside of therescue time tracker 10 to allow the rescue time tracker 10 to be affixedto the victim.

FIG. 2B shows the rescue timer 10 at the time that the device isinitialized and begins to track the time information for the victim 14.The removal of backing 24 initializes the rescue timer 10 and the timecounter 22 initially displays the total amount of time for potentiallyeffective treatment. The time period is preset such that initializationdoes not require the rescuer 12 to manually input the total time.Automatically initializing the rescue time tracker 10 using a pre-settime period on the rescue timer 12 can allow various rescuers andmedical personnel to have a known point of reference for the timedisplayed on the rescue timer 12. In this example, the rescue timer isinitially set to ninety minutes and counts down from ninety minutes.However, other time periods can be used. Exemplary time periods forvarious conditions are provided in the table below:

Condition Exemplary Time Period Cardiac Arrest 80-100 minutes (e.g., 90minutes) Stroke 45-90 minutes (e.g., 60 minutes) Additional time periodsor reminders can be set based on one or more of: 60 min door to needletime 25 min for CT scan or MRI after arrival at ED interpretation within45 min. 45 min for platelet counts. 10 min to patient evaluation afterED arrival. 15 min to notify stroke time after arrival. Myocardial80-100 minutes (e.g., 90 minutes) Infarction Additional time periods orreminders can be set based on one or more of: Door to balloon time of≦90 minutes fibrinolysis within 30 min if applicable (from EMS arrivalor hospital arrival) Trauma 45-90 minutes (e.g., 60 minutes)

FIG. 2C shows the rescue timer 10 at a time subsequent to initializationof the rescue timer. As shown in FIG. 2C and described above, a visualindicia (e.g., the coloration or shading of portion 20) can be used toindicate a critical time period. In some examples, the critical timeperiod can alert the rescuer to the end of the “golden hour” or the endof the first sixty minutes after major traumatic injury. As shown inFIG. 2C, for a rescue timer initially set to ninety minutes, the visualindicia is displayed after one hour, namely at 30 minutes remaining.While the example shown in FIG. 2C applies a visual indicia to indicatethe end of the “golden hour” other timer periods for applying visualindicia can be set based on the medical condition.

In some additional examples, multiple time periods each being associatedwith a different visual indicia can be displayed with the time count 22.

FIG. 3 shows another example of a rescue time tracker that includes adisplay portion 20 that provides a time counter 22. In contrast to theexemplary embodiments in which the rescue time tracker is included in asticker, the rescue time tracker shown in FIG. 3 is included in a band30 that can be placed around the hand or wrist of a victim. The band 30can be formed of plastic, silicone, or other materials.

In some additional examples, a rescue time tracker that includes adisplay portion that provides a time counter can be integrated into adefibrillation device. For example, the rescue time tracker can beincorporated into defibrillation electrode pads affixed to the victim'schest.

Referring to FIG. 4, in some examples, rescue time trackers can bedeployed at the scene of a mass emergency or mass casualty event toprovide rescue workers with information about the victims. For example,multiple victims 50 a-50 e can each be labeled with a rescue timetracker 52 a-52 e that provides an indication of an amount of time thathas elapsed since a rescue worker was first in contact with the victim.The times on the rescue time trackers can help the rescue workers toprioritize treatment of the victims 50 a-50 e.

In some examples, each of the rescue time trackers 52 a-52 e can includea locator that communicates wirelessly with a computing device (notshown). For example, the locator can be a GPS device that provideslocation information to the computing device. Alternatively, the locatorcan be a RFID device that provides location information to the computingdevice. Upon receipt of location information from multiple trackers 52a-52 e, as shown in FIG. 5, the computing device generates a userinterface that includes a map 60 and indicators 54 a-54 c identifyingthe relative locations of the victims 50 a-50 e on a grid 62.

In some examples, the rescue time trackers 52 a-52 e can additionallytransmit the time kept on the rescue time tracker to the computingdevice and the indicators 54 a-54 c displayed on the map 60 can includean indication of the time associated with each rescue time tracker 52a-52 e. By providing the time associated with each rescue time trackeron the map 60, a rescuer can more readily assess where he/she is mostneeded.

In some implementations, additional visual indicia (e.g., color coding,blinking indicators, different indictors) can be provided based on thetime of the associated rescue time tracker. For example, in FIG. 5,indicators 54 c and 54 e are shown with a thicker circle to indicatethat a greater amount of time has passed in relation to the other rescuetime trackers.

A rescuer can additionally possess or wear a locator device such thatthe map 60 can include visual indicia 56 representing the location ofthe rescuer (or multiple rescuers). This can allow a rescuer todetermine his/her location relative to the locations of the victims.

In some additional examples, other information to aid the rescuer can bedisplayed on the map 60. For example, icons representing variousequipment can be provided such as icons having thunderbolts on themrepresent AED's that a responder may grab and take to the victim 102when the victim has suffered a sudden cardiac arrest. Icons having a “+”on them may represent first aid kits that responders could use tobandage or otherwise treat victims of an accident. Examples ofadditional information that can be displayed on the map with thelocation information from the rescue time trackers is described forexample in U.S. patent application Ser. No. 12/946,803 filed on Nov. 15,2010 and entitled “Community Based Rescue,” the contents of which arehereby incorporated by reference in its entirety.

Referring now to FIG. 6A, in some embodiments, a rescue time trackerdevice 10 can include a display portion 20 that provides a time counter22 (e.g., such as the time counter 22 described herein) and additionalinputs/displays to capture/record/display time information for majorevents in the treatment of the victim. In the example of FIG. 5, therescue time tracker 10 includes display portions 70 a, 70 b, 70 c, and70 d that provide timing information about major events such asinitiation of CPR (display portion 70 a), defibrillation (displayportion 70 b), loading of the patient into an ambulance (display portion70 c), and drug administration (display portion 70 d). A rescuer canrecord/store time information for each of the major events by pressingan associated button or other input device on the rescue time trackerdevice 10. In the example of FIG. 5, the rescue time tracker 10 includesbuttons 72 a, 72 b, 72 c, and 72 d and depressing the button stores thecurrent time of the time counter 22.

In some additional examples, the rescue time tracker can include analarm or other visual or audio indicator. The alarm can be set to reminda rescuer to perform a particular action. For example, at the scene of amass casualty, the alarm could remind rescuers to deliver drugs, hang anew IV bag, refill a gas line, etc.

While the example of FIG. 5 included input devices to captureinformation about CPR, defibrillation, loading of a patient into anambulance, and drug administration, other information can be stored bythe rescue time tracker device 10. For example, ROSC, arrival ED,cooling started, advanced airway placement.

In some embodiments, it can be beneficial to transfer the data from therescue time tracker 10 to another computing device and/or to synchronizethe time information from the rescue time tracker 10 to a currentstandard time (e.g., a current absolute/solar time such as the time keptby a clock as opposed to a count of hours and minutes from a referencetime, to). In order to transfer the information from the rescue timetracker 10 to the computing device, the rescue time tracker 10 caninclude a wireless transmitter and/or in input/output port configured totransmit the data.

FIG. 7 shows and exemplary process for synchronizing time informationfrom a rescue time tracker 10 with a standard time and generating atimeline of events related to the treatment of the victim. The processbegins with the identification of a victim and the initialization orstarting of the timer (block 100). As described above, the timer can beinitialized by removing a backing from the device, pulling a tab toallow contact with a battery, or by selecting a start button.

At block 102, the rescue time tracker device receives and stores timeinformation related to various events. As described above, the timeinformation for various events can be captured from the timer based ondepression of a button or other input provided by the rescuer.

At block 104, the victim arrives at a treatment facility such as ahospital, medical facility, or ambulance.

At block 106, the time kept by the rescue time tracker is synchronizedwith a standard time kept by the treatment facility. Synchronizing therescue time tracker and the standard time can include associating acurrent time count on the rescue time tracker with a current standardtime of the treatment facility.

For example, referring back to the example of FIG. 6A, rescue timetracker 10 was initialized to a time of 90:00 and counted down to thecurrent time of 32:00. Thus, the time of 32:00 can be equated to acurrent, standard time of the treatment facility. This current, standardtime of the treatment facility can subsequently be used as a referencetime for calculating relative times for events. For example, assumingthe current time at the treatment facility is 6:00 pm EST, the time of32:00 can be associated with the standard time of 6:00 pm EST (as shownin FIG. 6B).

At block 108, event data from the rescue time tracker is transferredfrom the rescue time tracker to a computing device. For example, thetime data from the rescue time tracker and an identification of therelevant event can be transferred to the computing device using a wiredor wireless interface.

At block 110, the computing device calculates standard times for theevents based on the time information received from the rescue timetracker and the determined reference time. More particularly, thecomputing device determines the amount of between a particular event andthe reference time. For example, a difference between the timer countassociated with the reference time (e.g., as determined at block 106)can be calculated and the same difference can be applied to thereference time to determine an actual, standard time for the event.

For example, referring back to the example of FIG. 6A, rescue timetracker 10 captured timing data of 88:24 for initiation of CPR, 72:06for defibrillation, and 64:52 for ambulance. The, the time of 32:00 wasequated to a current, standard time of 6:00 pm EST. Thus, timinginformation for the events can be determined relative to the 6:00 pm ESTreference time. Using the example of the CPR initiation, 56 minutes and24 seconds elapsed between the initiation of CPR (88:24) and thereference time associated with a time count (32:00). Thus, as shown inFIG. 6B, a standard time of 56 minutes and 24 seconds before thereference time of 6:00 pm EST (e.g., 5:04 pm EST) can be associated withthe initiation of CPR.

At block 112, the computing device generates a timeline of events basedon the calculated times. The timeline of events can be displayed on auser interface of the computing device. An exemplary timeline is shownin FIG. 6B.

In some aspects, the timing information and other information (ifapplicable) from the rescue timer is combined with relevant data frommultiple, other EMS devices (including but not limited to adefibrillator monitoring a patient, a patient charting device, dispatchinformation device, and a navigation device). A system organizes andstores the information, and displays it in real-time on a screen in theback of an ambulance, to a hospital, and/or other location such as aphysician's home, via a web browser interface. Thus, the informationfrom the rescue timer can be incorporated into a larger set of patientdata gathered from multiple, different devices used in the treatment ofthe patient. An exemplary system for combining information from multipledifferent devices is described, for example, in U.S. 61/322,678 filed onApr. 9, 2010 and titled “SYSTEMS AND METHODS FOR COLLECTION,ORGANIZATION AND DISPLAY OF EMS INFORMATION,” the contents of which arehereby incorporated by reference. For example, the rescue timerdescribed herein can be communicatively coupled to the system describedin U.S. 61/322,678 to allow timing information from the rescue timer tobe incorporated with other information gathered about a patient andtreatment of the patient.

FIG. 8 shows an example of a generic computer device 600 and a genericmobile computer device 650, which may be used with the techniquesdescribed here. Computing device 600 is intended to represent variousforms of digital computers, such as laptops, desktops, workstations,personal digital assistants, servers, blade servers, mainframes, andother appropriate computers. Computing device 650 is intended torepresent various forms of mobile devices, such as personal digitalassistants, cellular telephones, smartphones, and other similarcomputing devices. The components shown here, their connections andrelationships, and their functions, are meant to be exemplary only, andare not meant to limit implementations of the inventions describedand/or claimed in this document.

Computing device 600 includes a processor 602, memory 604, a storagedevice 606, a high-speed interface 608 connecting to memory 604 andhigh-speed expansion ports 610, and a low speed interface 612 connectingto low speed bus 614 and storage device 606. Each of the components 602,604, 606, 608, 610, and 612, are interconnected using various busses,and may be mounted on a common motherboard or in other manners asappropriate. The processor 602 can process instructions for executionwithin the computing device 600, including instructions stored in thememory 604 or on the storage device 606 to display graphical informationfor a GUI on an external input/output device, such as display 616coupled to high speed interface 608. In other implementations, multipleprocessors and/or multiple buses may be used, as appropriate, along withmultiple memories and types of memory. Also, multiple computing devices600 may be connected, with each device providing portions of thenecessary operations (e.g., as a server bank, a group of blade servers,or a multi-processor system).

The memory 604 stores information within the computing device 600. Inone implementation, the memory 604 is a volatile memory unit or units.In another implementation, the memory 604 is a non-volatile memory unitor units. The memory 604 may also be another form of computer-readablemedium, such as a magnetic or optical disk.

The storage device 606 is capable of providing mass storage for thecomputing device 600. In one implementation, the storage device 606 maybe or contain a computer-readable medium, such as a floppy disk device,a hard disk device, an optical disk device, or a tape device, a flashmemory or other similar solid state memory device, or an array ofdevices, including devices in a storage area network or otherconfigurations. A computer program product can be tangibly embodied inan information carrier. The computer program product may also containinstructions that, when executed, perform one or more methods, such asthose described above. The information carrier is a computer- ormachine-readable medium, such as the memory 604, the storage device 606,memory on processor 602, or a propagated signal.

The high speed controller 608 manages bandwidth-intensive operations forthe computing device 600, while the low speed controller 612 manageslower bandwidth-intensive operations. Such allocation of functions isexemplary only. In one implementation, the high-speed controller 608 iscoupled to memory 604, display 616 (e.g., through a graphics processoror accelerator), and to high-speed expansion ports 610, which may acceptvarious expansion cards (not shown). In the implementation, low-speedcontroller 612 is coupled to storage device 606 and low-speed expansionport 614. The low-speed expansion port, which may include variouscommunication ports (e.g., USB, Bluetooth, Ethernet, wireless Ethernet)may be coupled to one or more input/output devices, such as a keyboard,a pointing device, a scanner, or a networking device such as a switch orrouter, e.g., through a network adapter.

The computing device 600 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as astandard server 620, or multiple times in a group of such servers. Itmay also be implemented as part of a rack server system 624. Inaddition, it may be implemented in a personal computer such as a laptopcomputer 622. Alternatively, components from computing device 600 may becombined with other components in a mobile device (not shown), such asdevice 650. Each of such devices may contain one or more of computingdevice 600, 650, and an entire system may be made up of multiplecomputing devices 600, 650 communicating with each other.

Computing device 650 includes a processor 652, memory 664, and aninput/output device such as a display 654, a communication interface666, and a transceiver 668, among other components. The device 650 mayalso be provided with a storage device, such as a microdrive or otherdevice, to provide additional storage. Each of the components 650, 652,664, 654, 666, and 668, are interconnected using various buses, andseveral of the components may be mounted on a common motherboard or inother manners as appropriate.

The processor 652 can execute instructions within the computing device650, including instructions stored in the memory 664. The processor maybe implemented as a chipset of chips that include separate and multipleanalog and digital processors. The processor may provide, for example,for coordination of the other components of the device 650, such ascontrol of user interfaces, applications run by device 650, and wirelesscommunication by device 650.

Processor 652 may communicate with a user through control interface 658and display interface 656 coupled to a display 654. The display 654 maybe, for example, a TFT LCD (Thin-Film-Transistor Liquid Crystal Display)or an OLED (Organic Light Emitting Diode) display, or other appropriatedisplay technology. The display interface 656 may comprise appropriatecircuitry for driving the display 654 to present graphical and otherinformation to a user. The control interface 658 may receive commandsfrom a user and convert them for submission to the processor 652. Inaddition, an external interface 662 may be provided in communicationwith processor 652, so as to enable near area communication of device650 with other devices. External interface 662 may provide, for example,for wired communication in some implementations, or for wirelesscommunication in other implementations, and multiple interfaces may alsobe used.

The memory 664 stores information within the computing device 650. Thememory 664 can be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. Expansion memory 674 may also be provided andconnected to device 650 through expansion interface 672, which mayinclude, for example, a SIMM (Single In Line Memory Module) cardinterface.

Such expansion memory 674 may provide extra storage space for device650, or may also store applications or other information for device 650.Specifically, expansion memory 674 may include instructions to carry outor supplement the processes described above, and may include secureinformation also. Thus, for example, expansion memory 674 may beprovided as a security module for device 650, and may be programmed withinstructions that permit secure use of device 650. In addition, secureapplications may be provided via the SIMM cards, along with additionalinformation, such as placing identifying information on the SIMM card ina non-hackable manner.

The memory may include, for example, flash memory and/or NVRAM memory,as discussed below. In one implementation, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 664, expansionmemory 674, memory on processor 652, or a propagated signal that may bereceived, for example, over transceiver 668 or external interface 662.

Device 650 may communicate wirelessly through communication interface666, which may include digital signal processing circuitry wherenecessary. Communication interface 666 may provide for communicationsunder various modes or protocols, such as GSM voice calls, SMS, EMS, orMMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others.Such communication may occur, for example, through radio-frequencytransceiver 668. In addition, short-range communication may occur, suchas using a Bluetooth, WiFi, or other such transceiver (not shown). Inaddition, GPS (Global Positioning System) receiver module 670 mayprovide additional navigation- and location-related wireless data todevice 650, which may be used as appropriate by applications running ondevice 650.

Device 650 may also communicate audibly using audio codec 660, which mayreceive spoken information from a user and convert it to usable digitalinformation. Audio codec 660 may likewise generate audible sound for auser, such as through a speaker, e.g., in a handset of device 650. Suchsound may include sound from voice telephone calls, may include recordedsound (e.g., voice messages, music files, etc.) and may also includesound generated by applications operating on device 650.

The computing device 650 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 680. It may also be implemented as part of asmartphone 682, personal digital assistant, or other similar mobiledevice.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), and theInternet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

A number of embodiments have been described. Nevertheless, it will beunderstood that various modifications may be made without departing fromthe spirit and scope of the invention. For example, much of thisdocument has been described with respect to smartphones and similarclient devices, but other forms of devices may be employed

In addition, the logic flows depicted in the figures do not require theparticular order shown, or sequential order, to achieve desirableresults. In addition, other steps may be provided, or steps may beeliminated, from the described flows, and other components may be addedto, or removed from, the described systems. Accordingly, otherembodiments are within the scope of the following claims.

1. (canceled)
 2. A computing device for communicating with a rescue timetracker device, the computing device comprising: a transceiver; one ormore processors; a memory; a communication interface coupled to thetransceiver, wherein the communication interface is configured toreceive time tracking information from the rescue time tracker device,the time tracking information comprising: at least one interval ofelapsed time indicative of a time period between a first rescue-relatedevent and a second rescue-related event, and information correspondingto one or more of the first rescue-related event and the secondrescue-related event; and a display configured to display the at leastone interval of elapsed time and the information corresponding to theone or more of the first rescue-related event and the secondrescue-related event and further configured to provide a reminder for arescuer to perform the second rescue-related event when the time periodhas concluded, wherein the rescue time tracker device is coupled to adefibrillation device.
 3. The computing device of claim 2 wherein the atleast one interval of elapsed time is an elapsed time from aninitialization of the rescue time tracker device and the firstrescue-related event is the initialization of the rescue time trackerdevice.
 4. The computing device of claim 2 wherein the reminder is analarm associated with the second rescue-related event.
 5. The computingdevice of claim 2 wherein the at least one interval of elapsed timecorresponds to a difference between a first time quantity at aconclusion of the at least one interval of elapsed time and a secondtime quantity at an initialization of the at least one interval ofelapsed time and further wherein the one or more processors areconfigured to: convert the first time quantity to a first standard timeassociated with a treatment facility, convert the second time quantityto a second standard time associated with the treatment facility basedon the first standard time, and generate a timeline indicating the firststandard time, the second standard time, the one or more of the firstrescue-related event and the second rescue-related event, and anassociation between the first standard time, the second standard time,and the one or more of the first rescue-related event and the secondrescue-related event.
 6. The computing device of claim 5 wherein thefirst standard time associated with the treatment facility is a time ofarrival at the treatment facility of a patient associated with at leastone rescue time tracker device.
 7. The computing device of claim 5wherein the second standard time is a time prior to a time of arrival ofa patient at the treatment facility.
 8. The computing device of claim 5wherein the display is configured to display the timeline.
 9. Thecomputing device of claim 5 wherein the communication interface isconfigured to receive patient data from one or more computing devicescomprising one or more of a defibrillator monitoring a patient, apatient charting device, a dispatch information device, and a navigationdevice and the one or more processors are configured to combine thepatient data with the timeline.
 10. The computing device of claim 9wherein the communication interface is configured to send one or more ofthe patient data and the timeline to a remote computing deviceassociated with at least one of an ambulance, a hospital, or aphysician.
 11. The computing device of claim 9 wherein the communicationinterface is configured to send, via a web browser interface, the one ormore of the patient data and the timeline to a display screen associatedwith the at least one of an ambulance, a hospital, or a physician. 12.The computing device of claim 9 wherein the communication interface isconfigured to send, in real time, the one or more of the patient dataand the timeline to a display screen associated with the at least one ofan ambulance, a hospital, or a physician.
 13. The computing device ofclaim 2 wherein the communication interface is configured to receivepatient data from one or more computing devices comprising one or moreof a defibrillator monitoring a patient, a patient charting device, adispatch information device, and a navigation device.
 14. The computingdevice of claim 2 wherein the information corresponding to the one ormore of the first rescue-related event and the second rescue-relatedevent comprises rescue-related event identification, rescue-relatedevent time of occurrence, and a rescue-related event alarm.
 15. Thecomputing device of claim 2 wherein the at least one interval of elapsedtime is a time interval corresponding to a medical condition of avictim.
 16. The computing device of claim 2 wherein the firstrescue-related event and the second rescue-related event comprise one ormore of an initialization of the rescue time tracker, cardiopulmonaryresuscitation (CPR), defibrillation, drug administration, return ofspontaneous circulation (ROSC), emergency department (ED) arrival,cooling, airway placement, a diagnostic scan, dispatching emergencyresponse personnel, powering on a defibrillator, loading a victim intoan ambulance, a delivery of drugs, hanging an intravenous bag, andrefilling a gas line.
 17. The computing device of claim 16 wherein thefirst rescue-related event comprises the initialization of the rescuetime tracker device.
 18. The computing device of claim 16 wherein thesecond rescue-related event comprises the delivery of drugs.
 19. Thecomputing device of claim 2 wherein the communication interface isconfigured to receive location information from the rescue time trackerdevice.
 20. The computing device of claim 19 wherein the locationinformation is global positioning system (GPS) information or a radiofrequency identification (RFID) information.